home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19970326-19970626
/
000109_news@columbia.edu _Mon Apr 21 17:18:21 1997.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Return-Path: <news@columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id RAA15156
for <kermit.misc@watsun.cc.columbia.edu>; Mon, 21 Apr 1997 17:18:20 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id RAA17122
for kermit.misc@watsun; Mon, 21 Apr 1997 17:18:20 -0400 (EDT)
Path: news.columbia.edu!panix!news.mathworks.com!news-peer.sprintlink.net!news.sprintlink.net!sprint!cs.utexas.edu!news.cs.utah.edu!cc.usu.edu!jrd
From: jrd@cc.usu.edu (Joe Doupnik)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Kermit 3.14 problems over TCPIP
Message-ID: <1997Apr21.095145.97219@cc.usu.edu>
Date: 21 Apr 97 09:51:45 MDT
References: <01bc51a4$040dc930$3bcf60cf@patrice>
Organization: Utah State University
Lines: 26
Xref: news.columbia.edu comp.protocols.kermit.misc:6927
In article <01bc51a4$040dc930$3bcf60cf@patrice>, "Patrice Levesque" <plevesque@videotron.ca> writes:
> Hi,
>
> I will appreciate if somebody can help me concerning a problem with Kermit
> 3.14.
>
> We are using MS-Kermit 3.14 over the network via TCP/IP with Windows
> Workgroup 3.11. It is working well but when we switch Kermit 3.14 (in a DOS
> Windows) in background, it will eventually disconnect from the server. The
> server is an Alpha 2100 with Open VMS 6.2.
>
> I did changes in the KERMIT.PIF file but I'm not able to correct the
> problem. Any suggestions.
>
------------
As you can imagine, Kermit must be given cpu cycles on a regular
basis if it is to maintain a TCP/IP connection. Giving those cycles is a
Windows configuration problem and I don't have a ready answer for how to
do that other than the obvious of checking the box saying it runs in the
background. A quick way of checking as you experiment with PIF settings
is to initiate a long file transfer, put MSK in the background, and then
bring it to the foreground to see how much work has transpired. In the past
this used to work fine when MSK was reduced to an icon, but one's Win 3.11
settings vary considerably from one installation to another. I haven't
checked this recently (no changes to MSK which should make a difference here).
Joe D.